Hi, We have two exchange 2007 orgs (e.g: A.Y, b.Z) and we are migrating users form A.Y to B.Z on a small groups, we have the two orgs in coexistence (A.Y send/receive B.Z send only). The issue is with some of the migrated users mailboxes they sometimes return the following NDR #< #5.2.0 smtp;550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:E0240000, 17.27161:0000000078000000000000002E00000000000000, 255.23226:00000000, 255.27962:0A000000, 255.27962:25000000, 255.17082:0F010480, 0.27745:80030400, 4.21921:0F010480, 255.27962:FA000000, 255.1494:15000000, 255.26426:25000000, 4.9780:BFF9FFFF, 4.14900:0F010480, 4.1509:0F010480, 4.7950:0F010480, 255.1750:00000000, 0.26849:0F010480, 255.21817:0F010480, 0.17361:0F010480, 4.19665:0F010480".> #SMTP# I've tried to look it up but no luck. Two weeks ago we lost "deleted by mistake" the exchange logs and we had to restore them using recovery software and the databases where uncountable and we had to use ESEUTIL to repair the dbs. Please if you have any ideas I'll be very grateful. Thanks in advance.

On Sat, 16 Oct 2010 11:22:18 +0000, Fi-zabadi wrote: >Hi, We have two exchange 2007 orgs (e.g: A.Y, b.Z) and we are migrating users form A.Y to B.Z on a small groups, we have the two orgs in coexistence (A.Y send/receive B.Z send only). The issue is with some of the migrated users mailboxes they sometimes return the following NDR #< #5.2.0 smtp;550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:E0240000, 17.27161:0000000078000000000000002E00000000000000, 255.23226:00000000, 255.27962:0A000000, 255.27962:25000000, 255.17082:0F010480, 0.27745:80030400, 4.21921:0F010480, 255.27962:FA000000, 255.1494:15000000, 255.26426:25000000, 4.9780:BFF9FFFF, 4.14900:0F010480, 4.1509:0F010480, 4.7950:0F010480, 255.1750:00000000, 0.26849:0F010480, 255.21817:0F010480, 0.17361:0F010480, 4.19665:0F010480".> #SMTP# I've tried to look it up but no luck. Two weeks ago we lost "deleted by mistake" the exchange >logs and we had to restore them using recovery software and the databases where uncountable and we had to use ESEUTIL to repair the dbs. Please if you have any ideas I'll be very grateful. Thanks in advance. After you repaired the databases, what else did you do to them? You know that you don't want to keep a repaired database in production, right? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

After we lost the logs the dbs disappeared, so we did the following: 1. restored the logs to a different path on the server. 2. copied the logs back to the original place, and suddenly the dbs appeared but were un-mountable. 3. Copied the dbs to a different path and ran the Eseutil command to repair the dbs. 4. Copied the dbs to the original place and mounted them. Is there something we should have done!!

On Sun, 17 Oct 2010 07:27:46 +0000, Fi-zabadi wrote: > > >After we lost the logs the dbs disappeared, so we did the following: > >1. restored the logs to a different path on the server. > >2. copied the logs back to the original place, and suddenly the dbs appeared but were un-mountable. > >3. Copied the dbs to a different path and ran the Eseutil command to repair the dbs. When you say "repaired" does that mean you ran "eseutil /p"? >4. Copied the dbs to the original place and mounted them. > >Is there something we should have done!! If you truely "repaired" the database then you should get a backup of the database now. Don't wait. After that, dismount it, run "eseutil /d" against the databse, and then run "isinteg -fix -test alltests" on the database -- at least twice. You want to see where isinteg either returns zero error and zero fixes, or at least where the errors and fixes keep the same values between runs of isinteg. The database should be mountable and at least serviceable at this point, but you really want to continue with the rest of the process and move all the mailboxes on that database to another database. Once the repaired database is empty you can delete it. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP